fix(app): showSession() on openTerminal error path - #19
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds 2 missing `showSession(sessionId)` calls on the error paths of `launchNewSession` and `openSession` in `public/app.js`.
Why
When `openTerminal` fails (e.g. a deleted worktree, missing project path), the error message is written to the terminal entry's buffer but the terminal is never shown — so the user sees nothing. This change makes the failing terminal visible so the error text is actually surfaced.
Bonus sub-fix lifted out of upstream PR #35 (@HaydnG). Independently useful regardless of whether the full remap feature lands.
Risk
Trivial — 2 lines, both in error branches that already populate the terminal buffer. `showSession` already runs on the success paths.